IBIS Macromodel Task Group Meeting date: 08 March 2011 Members (asterisk for those attending): Agilent: Fangyi Rao Radek Biernacki Ansoft: Chris Herrick Danil Kirsanov Ansys: * Samuel Mertens * Dan Dvorscak Deepak Ramaswamy Jianhua Gu Cadence Design Systems: Terry Jernberg * Ambrish Varma Celsionix: Kellee Crisafulli Cisco Systems: * Mike LaBonte Stephen Scearce Ashwin Vasudevan Ericsson: Anders Ekholm IBM: Greg Edlund Intel: Michael Mirmak LSI Logic: Wenyi Jin Mentor Graphics: * John Angulo Vladimir Dmitriev-Zdorov Zhen Mu * Arpad Muranyi Micron Technology: Randy Wolff Nokia-Siemens Networks: * Eckhard Lenski Sigrity: Brad Brim Kumar Keshavan * Ken Willis SiSoft: * Walter Katz Mike Steinberger Todd Westerhoff ST Micro: Syed Sadeghi Teraspeed Consulting Group: Scott McMorrow * Bob Ross TI: Casey Morrison Alfred Chong Vitesse Semiconductor: Eric Sweetman Xilinx: Mustansir Fanaswalla The meeting was lead by Arpad Muranyi ------------------------------------------------------------------------ Opens: - None -------------------------- Call for patent disclosure: - None ------------- Review of ARs: - Bob check BIRD 127 for type clarification possibilities - In progress - Ken draft BIRD - Done - Ambrish draft BIRD for relationship between Type and Format (row 25) - About to be sent to Arpad for review - Bob write a BIRD on correcting Table 1-3 in the spec. (Row 23). - In progress ------------- New Discussion: Arpad: We should continue the crosstalk discussion begun in email - Ken: The EDA tools should decide which are the aggressor TX channels - Arpad: Should we remove the sentence about number of matrix items? - Walter: Nothing says the TX matrix has to be the same size as the RX - Ken: We concluded the EDA tool can figure this out - Arpad: The sentence is not clear if it means one matrix must not change size while the DLL is executing. - Radek: What does "items" mean? - Arpad: Columns - Ambrish: It is implied this is about AMI_Init - Arpad: Do we need a reserved parameter for this? - Walter: We do not need another reserved parameter - It is easy to see which are the aggressors - Arpad: Is this draft ready? - Walter: A graphic depiction would help - Ken: I can add something to it - Arpad: Are we ready to vote? - Ambrish: Would like more explanation from Walter about aggressors - Walter: We have a max aggressors reserved parameter - There is also an actual number of aggressors - Radek: How do we say there are no aggressors? - Walter: The parameter can be zero - Arpad: The too will build separate matrices for the victim and aggressors - Radek: That's fine - Bob: The flow description is not in section 10 as stated - Walter motioned to vote to submit - Radek opposed, asking for more time - Walter withdrew his motion Walter: The initial intent of Tables was for clock jitter PDF - Now people are using it for other purposes - Ambrish gave an example - These uses don't follow the BNF - Ambrish: The model maker decides if it will be multiple rows - The tool only has to pass the right parameter string, unchanged - Walter: If multiple rows there are extra parentheses - If one row they are left out - This must be defined - Ambrish: I don't see anything that is broken - Bob: If there is more than one row we don't know where the break is - It was only well defined for PDF - Ken: We saw it as more general - Walter showed the examples from Ambrish - Arpad: Should the parentheses be put around single rows? - Walter: That would be consistent - Ambrish: We could not require row name for single rows - Bob: We could called for one row per line - Radek: The data could be different from item to item - Walter: It doesn't matter if it is an In param - Arpad: It does matter if it is Info - Walter described ideas for conveying type information - Arpad: We only need to describe the first column - The AMI and DLL writers are the same person - There is no concern about misunderstanding there - Walter: We should not allow Info Table Model Specific parameters - Arpad: What if we want to have reserved parameters like that - Walter: Maybe it should become reserved - Also it might go in the dependency table - Arpad: Some info parameters don't go to the tool or the model - There should be another Usage type for dependency tables - Bob: Labels are not sent to the tool - The tool should not need that - Table should be only Info or Input form here on AR: Ambrish draft update BIRD for Table syntax Arpad: Should we say something about changing block sizes? - Walter: The tool can make all the block sizes it wants - We should specify that AR: Arpad draft BIRD language for block size changes Walter: I wrote language that AMI_Close can write data to a file - A parameter would ask the EDA tool to display values - For example, DFE taps - There could be a file .labels - Tied into BIRD 121 - Arpad: We can continue this by email ------------- Next meeting: 15 Mar 2011 12:00pm PT Next agenda: 1) Task list item discussions ------------- IBIS Interconnect SPICE Wish List: 1) Simulator directives